Skip to content

feat(agent): add AgentRegistry for centralized agent management #381

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

Vivek0712
Copy link

feat(agent): add AgentRegistry for centralized agent management

Introduces AgentRegistry, a lightweight and optional utility for registering, discovering, and session-scoping agents. Supports mapping tool subsets to agents and integrates with agent state and event loop patterns.


Description

This PR adds a new AgentRegistry class to the SDK, mirroring the design of the existing ToolRegistry but for agents. The registry provides:

  • Centralized registration and discovery of agents.
  • Optional session-scoped management, allowing agents to be grouped and managed per session or event loop.
  • The ability to map subsets of tools to specific agents, supporting specialization and isolation.
  • Clean integration with agent state and event loop patterns, while remaining lightweight and fully optional for simple use cases.
  • No changes to the default single-agent workflow; the registry is opt-in for advanced/multi-agent scenarios.

Related Issues

N/A

Documentation PR

N/A (to be created if/when feature is merged)

Type of Change

  • New feature

Testing

How have you tested the change?

  • Ran hatch fmt --formatter and hatch fmt --linter to ensure code style and linting compliance.

  • Ran hatch test to verify all unit tests pass.

  • (Optionally) Ran hatch run test-integ to verify integration tests.

  • Verified that the changes do not break functionality or introduce warnings in consuming repositories: agents-docs, agents-tools, agents-cli.

  • I ran hatch run prepare

Checklist

  • I have read the CONTRIBUTING document
  • I have added any necessary tests that prove my fix is effective or my feature works
  • I have updated the documentation accordingly
  • I have added an appropriate example to the documentation to outline the feature, or no new docs are needed
  • My changes generate no new warnings
  • Any dependent changes have been merged and published

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Introduces AgentRegistry, a lightweight and optional utility for registering, discovering, and session-scoping agents. Supports mapping tool subsets to agents and integrates with agent state and event loop patterns.
@yonib05
Copy link
Member

yonib05 commented Jul 22, 2025

Hey @Vivek0712 ,

Thank you so much for your contribution. This looks really cool and interesting I was wondering if you had the opertunity to look at some multi-agent primitives we released last week. This is the roadmap item #214 for context.

Docs: https://strandsagents.com/latest/documentation/docs/user-guide/concepts/multi-agent/agents-as-tools/

While I think this could be a direction, I think we want to see how multi-agent usage evolves before implementing something like what you are proposing.

@zastrowm zastrowm added the area-multiagent Multi-agent related label Jul 22, 2025
@Vivek0712
Copy link
Author

Hi @yonib05,

Thank you for the response!

Yes, I’ve taken a look at the latest multi-agent primitives, and I’ve already started incorporating them into some of my personal projects and they’re super intuitive and powerful to work with.

I completely agree that the evolution of these primitives could shape the direction of the AgentRegistry concept as well and I see potential for it to complement the primitives in more complex orchestration scenarios down the line.

Happy to align with the team’s direction and revisit this idea as multi-agent usage matures further!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-multiagent Multi-agent related
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants